User-Centred Requirements Handbook

The User Requirements Framework consists of three main phases. Each stage is broken down into a series of numbered sections, as shown below. The aim of the Method is to collect data (e.g. user characteristics) and to generate items (e.g. a usage case) for each section. The phases and sections within them are defined so that one naturally leads on to the next. However the process is flexible and the order in which each section is considered can vary as appropriate to the situation.

Phase 1. User context and Early design

• 1.1 Summarise project
• 1.2 Identify users and stakeholders
• 1.3 Specify user characteristics
• 1.4 Describe technical environment
• 1.5 Describe physical environment
• 1.6 Describe social and organisational environment
• 1.7 Identify user goals and tasks
• 1.8 Review current processes
• 1.9 Review similar systems and products
• 1.10 Produce design ideas and concepts
• 1.11 Perform expert review of designs
• 1.12 Move to Phase 2 ?

Phase 2. Prototype and User test

• 2.1 General usability goals and guidelines
• 2.2 Identify design constraints
• 2.3 Identify task scenarios
• 2.4 Propose new processes
• 2.5 Develop prototype
• 2.6 Test prototype with users
• 2.7 Review user cost/benefits
• 2.8 Move to Phase 3 ?

Phase 3. User requirements documentation

• 3.1 General system characteristics
• 3.2 Organisational structure
• 3.3 Task scenarios and interaction steps
• 3.4 Technical environment
• 3.5 System functions and features
• 3.6 User interface design
• 3.7 User Support
• 3.8 Physical environment
• 3.9 Social and organisational environment
• 3.10 Standards and styleguides to apply
• 3.11 Test plan
• 3.12 Implementation plan

The process is iterative so that items of information are noted, then modified or firmed up. For example, a broad set of system functions may be described in the project specification, then refined after the tasks have been analysed and a prototype developed.

The method of data collection is also flexible. While in some situations requirements can be generated through discussion, in others, the use of particular techniques and methods (e.g. task analysis) may be needed.

Collecting user requirements using this framework will demonstrate that a user-driven approach to capturing user requirements has been adopted, and will support the requirements of the ISO standard 9241, Part 11 (ISO, 1997a).

When collecting requirements information, a set of forms are presented which may be used to structure the information. An example completed form is normally given with a blank version in the Appendix 3 which may be photocopied. The forms can then be used as the basis for the user requirements document.

Phase 1: User context and Early design

PHASE 1 of the user requirements specification process consists of the first iteration around the user-centred design loop as shown below.

• CONTEXT: Background information is gathered about the project and what it is intending to achieve. A user and stakeholder analysis is then performed to identify the range of different users and stakeholders, and to document their characteristics. A description of the environment in which they are working is also produced. These contextual factors may highlight a need for particular user requirements.
• REQUIREMENTS: The next stage is to identify user goals and tasks for the system. The current process for each goal is reviewed, problems identified and ideas for overcoming the problems are listed. Similar systems or products on the market may also be reviewed to any identify functions or features that should be included or excluded from the new system.
• DESIGN: Using the information gathered thus far, a list of design ideas or a design concept may be produced and represented in different ways.
• TEST: The design ideas or concept may then be considered as part of an expert review in order to decide whether they form a good basis for meeting the user goals. If so then the process may move into Phase 2.

FIGURE 4. PHASE 1: USER CONTEXT AND EARLY DESIGN

1.1 Summarise project
Back to Contents